@DenisKelley Looking around, I found this github wiki article was updated in January.
https://github.com/owncloud/documentation/wiki/Uploading-files-up-to-16GB

Did you check the repos before calling me an ass or taking the word of some random person on a forum? I don't think so. You are so insistent that this is my fault and wanting to call me names that you are blindly willing to assume anything. Bottom line.... one official spokesperson for the company responded that the issue should not exist after asked directly if it was fixed. A random person on another forum made a comment about something that doesn't exist and you took their word for it as a reason to badger me.

Here are the full contents of the repo for those interested.

0_1463379259385_Screenshot from 2016-05-16 09:12:36.png

So where is the PHP7 package that you are berating me about? Please provide me the link as I cannot find it.

For those who were still having problems getting Mattermost running on CentOS 7, I was also having the same problems and couldn't get beyond the postgres install. I found another guide and with a few tweaks, I was able to get this running.

https://www.howtoforge.com/tutorial/install-mattermost-with-postgresql-and-nginx-on-centos7/

The change that was required from this guide was in the "Download and Extract Mattermost"

Instead of...
[root@mattermost ~]# wget -q "https://github.com/mattermost/platform/releases/download/v2.0.0/mattermost.tar.gz" -O mattermost.tar.gz

Use this...
wget https://releases.mattermost.com/3.3.0/mattermost-team-3.3.0-linux-amd64.tar.gz

Then in the next block, instead of...
tar -xvzf mattermost.tar.gz

Use this...
tar -xvzf mattermost-team-3.3.0-linux-amd64.tar.gz

After that, follow the guide to the letter and it will get you to this...
0_1473265786807_upload-d89fe07b-7d71-4d39-8dd7-e00395f6aa84

@aaronxiang @wirestyle22 @scottalanmiller

That's a good question... when does chrooting make more sense than containers today?

Storage is one. Lots of people use chroot jails for storage purposes. Containers are heavier than chrooting which has effectively no impact on any resources.

@BBigford said:

Looks like there is quite a bit included in the free version for up to 10 premium users, and 10 basic users. Interesting.

Yes, it is quite extensive.

@scottalanmiller said:

@travisdh1 said:

Thought I'd take a quick look at this. I like how the output looks, but agree that I wouldn't want to leave it running. The loadavg jumped just from starting to look at the output.

it would have to, that is a LOT of output!

Wow, you're not kidding about that. Even gives you the current available entropy from /proc/sys/kernel/random/entropy_avail. I've never seen something give you this much information and be so easy to get running.

@scottalanmiller Thanks for this post and answering all my questions. @travisdh1 Thanks for answering all my questions as well. Good Thread!

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

Scott, you mentioned that this is all at the kernel level - could you roll your own version of this?

Sure, you'd have to write your own storage layer, though. So it's not trivial in any way.

OH.. that's where I was confused I guess... I thought the storage layer was part of KVM (that's the hypervisor they use, right?)

Not part of KVM itself. The Scale HC3 is unique, there is no software version available on the market.

So they wrote the storage layer? Cool - good to know/understand that.

Yes, Scale is primarily a storage vendor. Before they made their Hyperconverged product, they made scale out storage only. That was before KVM was mature enough to make the HC3 product. They no longer sell the storage layer, it is now developed purely and designed solely around the needs of the HC3 product so is completely unique to that. It's the storage layer and the storage integration (and support) that are their selling points. That's what makes them special and unique. KVM and the hardware on its own you could do yourself and you could easily make due with a different interface.

@scottalanmiller

@scottalanmiller said:

We need some latency numbers from around the world. Anyone want to collect some for us?

Here is the first IP address. A long running ping (hundreds or thousands of pings) would be good, we need the final stats from that:

104.236.119.59 108.61.151.173 172.99.75.133

We have a good idea on bandwidth, IO, CPU and memory. Network latency is pretty huge.

1,200,000 packets later...
via rackspace 8 GB General Purpose v1 based in london

--- 162.242.243.171 ping statistics --- 400510 packets transmitted, 400499 received, 0% packet loss, time 400849652ms rtt min/avg/max/mdev = 79.018/79.634/184.775/2.778 ms --- 104.236.119.59 ping statistics --- 400759 packets transmitted, 400732 received, 0% packet loss, time 401132556ms rtt min/avg/max/mdev = 73.663/74.533/191.571/2.203 ms --- 108.61.151.173 ping statistics --- 400765 packets transmitted, 400749 received, 0% packet loss, time 401117767ms rtt min/avg/max/mdev = 69.861/75.792/205.164/3.167 ms

@dafyre said:

@JaredBusch said:

@dafyre said:

As a matter of correctness... Do you have EPEL /REMI or any other repos installed in your CentOS 7 image?

The script is connecting the Gitlab RPM, that is all. The base image he uses for all of these is CentOS 7 minimal, release 1511 unless he has changed the base template on his scale cluster.

Right. I'm just curious if he has added the epel-release or any other repos to it.

Definitely no EPEL. I often use it, but avoid it in the base image.

@scottalanmiller said:

Just tested and working great for me.

It makes the warning go away. No clue if it helps performance any.

If you want to enable PHP 7 you need to edit a different repo file to find the remi-php70 repo to enable.

nano /etc/yum.repos.d/remi-php70.repo

@scottalanmiller said:

@alex.olynyk said:

@dafyre said:

@alex.olynyk said:

@scottalanmiller said:

@alex.olynyk said:

@scottalanmiller said:

Are you using an extra app that is not part of ownCloud itself? What is the exact app?

no, users access OC using a browser

I don't mean an app for the users. i mean an app installed on ownCloud to provide the encryption.

0_1457640037846_Capture.PNG

Could that encryption application be what is blocking the file sharing?

maybe, but it wont let me disable it

That's not good. Perhaps because the content is already encrypted?

i disabled the module in the apps menu

@wirestyle22 said:

@coliver said:

@wirestyle22 said:

I have to look up SSL certification on CentOS 7 now. I've only ever done it on our Barracuda SSL VPN which was just an upload. Here we go

I think you need to look up SSL for Apache if you are trying to encrypt ownCloud. I think someone has a guide on here somewhere about it.

I think @JaredBusch has it in his 8.2 guide. I think he did self signed though. I'm unsure of how to do this on linux with digicert or something similar

It was a self signed for the example. but I use letsencrypt myself. Some clients using ownCloud have StartSSL certs.

I just used this myself to make a new block device in a single line. Awesome 🙂

@scottalanmiller said:

@JaredBusch said:

@scottalanmiller said:

@JaredBusch said:

@scottalanmiller said:

@JaredBusch said:

While I have never made a how to with a port range, the basic firewalld syntax is used all over the place on this forum by me and every system that I have ever seen that accepts a port range does so with the range hyphenated from lower boundary to upper boundary.

I would have thought that this was a colon, though, not a hyphen.

I have never seen it commonly used with a colon to represent a range

Native IPTables. 🙂

I rarely work with native IPTables. That would explain a difference in point of view.

Yeah, and for me I pretty much have done raw edits on /etc/sysconfig/iptables and never used external tools. Now with FirewallD I'm relearning the syntax for everything on Linux firewalls.

Well, at least I'm not the only one then. Learning how to use firewall-cmd still feels a bit odd.

In case anyone else runs across this same issue, I got this resolved with a simple command:

dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg

After doing this, everything booted up properly.

I then installed hyperv-daemons, rebooted, and everything works great.

@travisdh1 said in Installing Zimbra Email 8.6 on CentOS 7:

@scottalanmiller said in Installing Zimbra Email 8.6 on CentOS 7:

8.8.9 is out now...

https://files.zimbra.com/downloads/8.8.9_GA/zcs-NETWORK-8.8.9_GA_2055.RHEL7_64.20180703080917.tgz

8.8.10 is now out
https://files.zimbra.com/downloads/8.8.10_GA/zcs-8.8.10_GA_3039.RHEL6_64.20180928094617.tgz

There is also a patch for 8.8.10 as well
https://blog.zimbra.com/2018/10/new-zimbra-patches-8-8-10-patch-1-and-8-8-9-patch-6/

Bug found, scheduled for release in 4.15

https://xen-orchestra.com/forum/topic/159/nfs-connection-issue/46

Graylog has updated and no longer relies on the old version of ElasticSearch. It will use ElasticSearch 2 now. So time to revisit.